Google Links

Follow the links below to find material targeted to the unit's elements, performance criteria, required skills and knowledge

Elements and Performance Criteria

1. Gather and confirm client requirements
   • Confirm the requirements, and the scope, of the project with the client
   • Gather information regarding requirements via sources of information and business processes
   • Analyse client requirements, to determine the project scope and the problem context or opportunity faced by the business
   • Document the client requirements, project’s scope, related problems, and sources of information
2. Analyse the functional and related non-functional requirements
   • Map business processes using modelling tools such as unified modelling language (UML)
   • Determine the opportunities for business process efficiencies
   • Document functional, and related non-functional, processes
3. Analyse the feasibility of a project
   • Analyse the technical feasibility of the project
   • Analyse the operational feasibility of the project
   • Determine the budget and schedule feasibility of the project
   • Examine how the project will fit within the organisation
4. Develop high-level system solutions
   • Develop and document feasible solutions for client requirements
   • Explore and document the feasibility of each solution
   • Examine alternatives against project constraints
   • Document assumptions, dependencies and required resources
   • Produce a project risk analysis
   • Document future requirements
5. Prepare and publish the software-requirements documentation
   • Develop the software-requirements document
   • Submit the software-requirements report to the appropriate person for project approval

Performance Evidence

Evidence of the ability to:

Analyse client requirements to create a software requirements document, including:

gathering, confirming and documenting client requirements

analysing functional and related non-functional requirements, and project feasibility

developing high-level system solutions

submitting documents for approval.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

---

Knowledge Evidence

To complete the unit requirements safely and effectively, the individual must:

identify the client business domain

describe content features, such as clarity and readability

summarise the system's current functions

explain document design and usability

explain the functions and features, of templates and style guides

summarise instructional design principles

describe the role of stakeholders and the degree of stakeholder involvement

explain two or more current industry systems development methodologies.

---